Bump linq2db to 5.4.1.9 to fix assembly binding conflict#572
Merged
Aaronontheweb merged 1 commit intoFeb 15, 2026
Merged
Conversation
) linq2db changed their AssemblyVersion from 5.4.1.0 to 5.0.0.0 between package versions 5.4.1 and 5.4.1.9. Our packages compiled against 5.4.1 referenced AssemblyVersion 5.4.1.0, causing binding failures when NuGet resolved the newer 5.4.1.9 (AssemblyVersion 5.0.0.0). Recompiling against 5.4.1.9 resolves the mismatch.
This was referenced Feb 15, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #567
linq2dbfrom5.4.1to5.4.1.9inDirectory.Packages.propsto resolve assembly binding failuresRoot Cause
The linq2db project has
<Version>5.0.0.0</Version>hardcoded inDirectory.Build.propssince v5.0.0. Their CI pipeline usesSetVersion.ps1to patch this value at build time — for v5.4.1, CI set it to5.4.1, producing AssemblyVersion5.4.1.0.However, the
5.4.1.9package (published October 2025) was built without the CI version patching step — verified by theInformationalVersionin the shipped DLL (5.0.0.0+6b676b55...) which references commit6b676b55. As a result, it shipped with the unpatched AssemblyVersion5.0.0.0:linq2db 5.4.15.4.1.05.4.1linq2db 5.4.1.95.0.0.05.0.0.0Our packages were compiled against
5.4.1(AssemblyVersion5.4.1.0). When a user's project resolved the newer5.4.1.9via NuGet (satisfying>= 5.4.1), .NET refused to bind because5.0.0.0 < 5.4.1.0.Recompiling against
5.4.1.9makes our assembly referencelinq2db, Version=5.0.0.0, which resolves the mismatch.Test plan
dotnet buildsucceeds with 0 errorslinq2db, Version=5.0.0.0(not5.4.1.0)